🚨 [security] [backend] Update mongoose 6.0.8 → 7.2.2 (major) #227
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ mongoose (6.0.8 → 7.2.2) · Repo · Changelog
Security Advisories 🚨
🚨 Prototype pollution Schema.path in automattic/mongoose
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by 23 commits:
chore: release 7.2.2Merge pull request #13448 from Automattic/vkarpov15/gh-13334Merge pull request #13449 from Automattic/vkarpov15/gh-11187Update lib/connection.jsMerge pull request #13450 from Automattic/vkarpov15/gh-13434fix(update): allow setting paths with dots under non-strict pathsdocs(connections): add section on multi tenantMerge pull request #13447 from Automattic/vkarpov15/gh-13235chore: use node 14 for tsd tests because some upstream dep of tsd uses optional chainingdocs(connection+model): expand docs on accessors for underlying collectionsMerge pull request #13446 from Automattic/vkarpov15/gh-13421Merge pull request #13445 from Automattic/vkarpov15/gh-13409test: fix tests with tsd@0.28.1types: improve function parameter types for `ToObjectOptions` transform optionfix(schema): make bulkWrite updateOne() and updateMany() respect timestamps option when set by merging schemasMerge pull request #13441 from Automattic/vkarpov15/gh-13275Merge pull request #13444 from Automattic/vkarpov15/gh-13430Merge pull request #13440 from Automattic/vkarpov15/gh-13436-code-reviewdocs: add nextjs page with link to next starter app and couple FAQsfix(schema): recursively copy schemas from different modules when calling `new Schema()`Merge pull request #13439 from Automattic/vkarpov15/gh-13413-code-reviewrefactor(cursor): use arrow functions instead of `_this` throughouttest(findOneAndUpdate): add extra assertions from code review for #13437👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands